Protecting 3.7 TB of Project Data: The BIM 360 Data Migration Initiative

The BIM 360 Data Migration project addresses the challenge of managing 3.7 TB of project data stored in a locked in cloud platform - ‘BIM 360 Teams’ which became inaccessible as versions of Autodesk Revit 2017/2018 were phased out. This migration ensureed that all project data moved to the sucessor, ‘BIM 360 Docs’, upgrading models to the latest Revit versions and maintaining user access throughout the process.

WeWork

Programme Management

Operations

Case Study

Author

Eimhin Rafferty

Published

May 28, 2024

Modified

May 28, 2024

Streamlining 3.7 TB of Project Data: The BIM 360 Data Migration Initiative

Overview

The BIM 360 Data Migration project addresses the challenge of managing 3.7 TB of project data stored in BIM 360 Teams, which will become inaccessible as Revit 2017/2018 phases out. This migration ensures that all project data moves to BIM 360 Docs, upgrading models to the latest Revit versions and maintaining user access throughout the process.

Objectives

Data Transfer: Move all project data from BIM 360 Teams to BIM 360 Docs.
Model Upgrade: Upgrade EC, Layout, and AOR Revit models to the latest versions.
Access Maintenance: Ensure continuous access for users to the migrated projects.
Access Tracking: Maintain records of external access to projects in BIM 360 Teams.

Doing what we can to start

Challenges

Data Storage and Revit Versions

Data spans multiple platforms: BIM 360 Team, BIM 360 Docs, and W: Drive.
Various Revit versions are used, with Revit 2017 access ending by Q1 2021, impacting a significant number of projects.

Projects at Risk

317 projects using Revit <2016, 340 projects using Revit 2018, and 36 projects using Revit 2019 or later are at risk due to version phase-out and storage limitations.

Migration Process

overview of migration workflows

Stage 1: Data Transfer

Move Revit models, CADs, point clouds, and relevant files to BIM 360 Docs.

Stage 2: Model Upgrade

Upgrade all Revit models to the latest version (2019).
Unzip and organize composite design models.

Stage 3: Model Activation

Convert necessary Revit models to cloud collaboration models for design teams.

Automation and Management

A Forge API Python library automates data transfer, model upgrades, and collaboration tasks.
Airtable is used to manage data and project information efficiently.

Workflow

Transfer: Move files to an ARCHIVE folder in BIM 360 Docs.
Unzip: Unzip composite Revit models.
Upgrade: Use the Design Automation Forge API for remote upgrades.
Collaborate: Manually collaborate and link files in BIM 360 Docs.

Ongoing process improvement

Code Refinement: Improve version comparison, display name handling, and async processing.
Management Transition: Move project management from Airtable to Sheets.
Process Consolidation: Integrate unzip/upgrade processes and enhance performance.
Dashboard Development: Create a progress dashboard for real-time tracking and stakeholder updates.

Key Milestones

Initial EMEA Release: Establish transfer management and validation framework.
Speed Improvements: Implement AWS Lambda for efficient file transfer and remote upgrades.
Global Release: Expand process management globally and develop a reporting dashboard.
Process Refinement: Consolidate and integrate unzip/upgrade processes into the management system.

By successfully executing this migration, the project ensures that WeWork’s data remains accessible, updated, and efficiently managed across the latest BIM 360 platforms.

Archilogic Editor 4.0: A Comprehensive Rebuild

As the product manager in Archilogic, I oversaw the rebuild of Archilogic Editor 4.0, introducing a Spacegraph data structure for floor plans. This project enhanced efficiency and accuracy, improved data security, and streamlined workflows.

Eimhin Rafferty

Automating Space Calculation: A Case Study on Leading Innovation in Real Estate with Archilogic

As a Product Manager at Archilogic, I led the development of a groundbreaking product that automates space calculations based on BOMA standards. This product leverages the power of our Spacegraph data structure, making it scalable, repeatable, and uniquely effective due to the relational nature of the underlying data.

Eimhin Rafferty

Case Study: Automating Floor Plan Polylining and Integration with IWMS Platforms

As a Product Manager at Archilogic, I led the development and integration of a solution to automate floor plan updates for customers, addressing a major pain point: keeping floor plans updated across multiple platforms, particularly their Integrated Workplace Management Systems (IWMS). This case study details how we collaborated with customers using FM Systems, developed automation for polyline creation, integrated our solution with IWMS platforms, and ultimately built a native app plugin for seamless data transfer.

Eimhin Rafferty

Case Study: Enabling Multiple Layouts at Archilogic

In Archilogic, I led a transformative project called ‘Enable Multiple Layouts.’ This initiative aimed to allow users to create, review, and implement different layout options for building floors without disrupting the main production environment. The project involved significant technical complexity, including new API implementations and enhancements to our space graph data structure.

Eimhin Rafferty

Case Study: Implementing Design Standards for EMEA - A Design Technology Product Management Initiative at WeWork

As a Design Technology Product Manager at WeWork, I led a high-impact project to translate global design standards into actionable content, processes, and training systems for teams in EMEA. This initiative was configured to address local needs, supply chain demands, and building regulations, ensuring consistency and compliance across the region.

Eimhin Rafferty

Case Study: Transforming Design Technology Support at WeWork

As a Design Technology Product Manager at WeWork, I spearheaded a critical initiative to overhaul the support process for our design technology teams. Recognizing the need for a systematic approach to support as our teams grew leaner and more remote, I led the design, implementation, and operationalization of a comprehensive Jira-based ticketing system. This project highlighted themes of empathy, accountability, accuracy, and cross-functional leadership, ensuring fair and transparent support for all teams.

Eimhin Rafferty

Developing a Workflow Template for the Custom Enterprise Team

At WeWork, I was tasked with supporting a newly formed ‘Custom Enterprise’ team within the Sales Organisation. This team of six designers was responsible for rapidly creating sales collateral for various buildings in our portfolio. Assembled on an ad-hoc basis and not reporting to the main design organisation, they faced significant operational challenges.

Eimhin Rafferty

Handling a Global Software Failure: A Case Study

During a global software failure, I led the resolution efforts across multiple regions, including Japan, Asia, EMEA, LATAM, and North America. The issue was initially reported by a user in Japan and quickly spread to other regions. Coordinating with network engineers and resellers, I gathered detailed information from users and kept stakeholders informed throughout the process. By developing PowerShell scripts and SOPs for a complex uninstall process, and leveraging VP support to navigate legal restrictions, I ensured minimal downtime and restored normal operations efficiently.

Eimhin Rafferty

WeWork Self Serve Platform: Enhancing Access and Security

To address significant bottlenecks and security issues, I led the design and development of a self-serve web app integrated with Autodesk Construction Cloud. This platform revolutionized how our global design team accessed and managed 3D models of WeWork’s 550 buildings and 2500 floors, ensuring both security and efficiency.

Eimhin Rafferty